-
Notifications
You must be signed in to change notification settings - Fork 424
adds doc suggestions made on issue 3666 #3668
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Robert Kielty <[email protected]>
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hi @RobertKielty. Thanks for your PR. I'm waiting for a kcp-dev member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/ok-to-test |
|
Sorry, took as a bit to get to PR backlog |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A few suggestions. Let me know what you think? Im on the fence with my own suggesions, and happy to discuss why you came up into this page in the first place to change it :)
| kcp includes some, but not all, of the Kubernetes APIs. | ||
|
|
||
| ## (core) v1 | ||
| kcp does not make us of Kubernetes API endpoints that are concerned with orchestrating clusters and their workloads. Clusters dedicated to workload orchestration have these resources but kcp does not. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
this sounds bit of strange too.
I think we need to be more explicit:
kcp functions as a pure control plane, providing only a subset of the full Kubernetes API. It is not a complete Kubernetes distribution and intentionally excludes APIs related to running workloads.
Because kcp doesn't manage nodes or run containers, it lacks the necessary controllers and resource definitions for orchestration. Specifically, you will not find key resource types such as:
The apps API group (e.g., Deployments, StatefulSets, DaemonSets)
The core Pods resource
Networking resources like Services and Endpoints
You can find more details about the specific APIs kcp does support below.
|
|
||
| ## Kubernetes resources used by kcp | ||
|
|
||
| kcp makes use of these API Endpoints and resources to provide kcp features and indoing so leverages the Kubernetes Event Loop to manage non-cluster resources that can them be handles using conventions and tooling from the Kubernetes eco-system. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This sentence sounds strange. Do we even need this if we detalized above?
Summary
Re-write of the BuiltIn APIs page to make it more explicit.
What Type of PR Is This?
/kind documentation
Related Issue(s)
Fixes #3666
Release Notes